Map HTTP-related tests to web-features #56953
Conversation
wpt-pr-bot
requested review from
Manishearth,
annevk,
caitp,
jdm,
mnot,
wisniewskit,
youennf and
yutakahirano
jugglinmike
changed the title
|
@jugglinmike can you resolve conflicts? Normally I'd do it, but there are a bunch of directories here with "**" before where a decision needs to be made wrt overlapping tests or not. |
|
@foolip Three of the conflicts could be resolved by making exceptions for individual tests that have recently been attributed to other web-features. The other three are contestation for entire directories:
I originally proposed that these should be classified as That's why I removed those directories from this patch. Let me know what you think! |
|
I'm not clear on the exact boundary between fetch and HTTP in practice. In principle fetch is fairly simple and clearly sits on top of HTTP, but in some cases fetch overrides HTTP for reasons of web compat. I'll review and see if there are borderline cases left. |
foolip
left a comment
foolip
left a comment
There was a problem hiding this comment.
I have low confidence in what approach will stand the test of time here, and we've usually tended to avoid overlap, but when the boundary between features and specs isn't so clear, I'm not sure what to do.
|
@foolip Since we've generally taken pains to avoid overlapping classifications, I've included comments to demonstrate that these overlaps are intentional. |
4 participants
Hello, reviewers! As of 2025-12-05, the wpt-pr-bot is requesting reviews from code owners for changes to WEB_FEATURES.yml files. To learn more about the purpose of these files, check out this presentation from TPAC 2025, Annotating WPT to Surface the Status of the Platform.
Matching test files for HTTP authentication
./fetch/http-cache(12 non-matching test files hidden)
./fetch/api/credentials./xhr(192 non-matching test files hidden)
(99 non-matching test files hidden)